Supported Profile Fields
The following are the links to view the supported fields for Auto Entry for "Payables Transaction", "Receivings Transaction", "Receipt", and "Vendor" Record Types in Auto Entry for Dynamics GP (further divided based on different templates).
Record type - Payables Transaction
- Supported Profile fields for Payable Invoice Auto Entry Template
- Supported Profile fields for Enter Match Invoice Auto Entry Template
Record type - Receivings Transaction
- Supported Profile fields for Shipment Invoice Auto Entry Template
-
Supported Profile fields for Project Invoice Auto Entry Template
Record type - Receipt
Record type - Vendor
Auto Entry Scenarios:
The following are possible scenarios when you perform Auto Entry for GP:
Case 1: When you perform an Auto Entry without creating "Tax Schedule ID" field.
Result: Auto Entry will not calculate any Tax and the Tax Schedule field will remain blank.
Case 2: When you perform an Auto Entry after creating the "Tax Schedule ID" field (without entering any value) and select the Vendor that does not have any default "Tax Schedule ID".
Result: Auto Entry will not calculate any Tax and the Tax Schedule field will remain blank.
Case 3: When you perform an Auto Entry after creating the "Tax Schedule ID" field (without entering any value) and select the Vendor that has any default "Tax Schedule ID". Now, in the Tax Schedule ID, one of the Tax details has a value that is not supported by PaperSave.
Result: Auto Entry will throw an exception titled: PaperSave supports only Tax Details having Based On "Percent of Sale/Purchase" or "Tax Included with Item Price".
Case 4: When you perform an Auto Entry after creating "Tax Schedule ID" field (without entering any value) and select the Vendor that has any default "Tax Schedule ID". Now, in the Tax Schedule ID, one of Tax details that has "Percent of Sale/Purchase" or "Tax Included with Item Price" value.
Result: Auto Entry will calculate any Tax with Tax Schedule ID field defined for Vendor's Tax Schedule ID.
Case 5: When you perform an Auto Entry after creating "Tax Schedule ID" field and enter the value in that field. Now, in the Tax Schedule ID, one of the Tax details has the value that is not supported by PaperSave.
Result: Auto Entry will throw an exception titled: PaperSave supports only Tax Details having Based On "Percent of Sale/Purchase" or "Tax Included with Item Price".
Case 6: When you perform an Auto Entry after creating "Tax Schedule ID" field and enter the value in that field. Now, in the Tax Schedule ID, one of the Tax details has "Percent of Sale/Purchase" or "Tax Included with Item Price" value.
Result: Auto Entry will calculate any Tax with Tax Schedule ID field that is passed during Auto Entry.
Note: "PaymentTerms" Profile Field must be configured using following query:
select PYMTRMID from [SY03300]
The following are recommended guidelines for setting up Profile fields when performing Auto Entry:
-
The table name must not be same as one of the column name (for example, if the column name in the table is VendorName, then the table name must not be VendorName), else the column will lose its values after saving.
-
The profile field configured for Auto Entry must not be used as a table name.
-
All the required supported profile fields must be configured as specified in the supported profile fields for Auto Entry.
-
The following are columns under Distribution Table Type Profile field. The column names must be configured exactly the same as mentioned in the Supported Profile fields.
- Account Number
- Reference (Optional)
- Type
- Debit Amount
- Credit Amount
- Distribution Reference (Optional, max 30 characters allowed)
The following section includes some of the commonly encountered errors while performing Auto Entry and their possible reasons:
Error Message | Reason |
Account not found in Account Index | Account number was not included in Distribution lookup. |
No valid Exchange Rate found for the specified Document Date | The vendor has entered the wrong currency. |
Item not found in database | PaperSave Auto Entry Client is not installed on the server. |